YARBO OPEN PLATFORM · SDK + HARDWARE KIT (HDK)

One Yarbo, more possibilities

Yarbo Open Platform Beta is now open—combining our SDK and Hardware Kit (HDK) so you can build custom automations, smart integrations, and purpose-built attachments on one modular yard robot.

  • SDK
  • Hardware Kit (HDK)
  • RTK & Vision
  • Maps, Control & MCP
PRIVATE BETA COHORT INVITES

Join the private beta

Why We Opened Yarbo

A modular robot shouldn’t stop at the attachments we build.

Yarbo is a heavy-duty tracked base—not a sealed single-purpose appliance. We’re opening our software and hardware interfaces, with safety interlocks built in, so you never have to build an outdoor robot from scratch.

Co-create custom attachments

Bolt onto 3D CAD mounts, switched power, CAN & Ethernet to prototype custom yard or field tools.

Learn & validate outdoor robotics

Test perception, navigation, and control algorithms on real terrain using centimeter RTK & stereo vision.

Automate on your own terms

Build local dashboards, smart-home routines, or AI workflows with our SDK & ready-to-use MCP.

Open to build on. Isolated so your robot stays safe.

CRASH-ISOLATED SANDBOX · HARDWIRED INTERLOCKS
ENTRY 01 · OFF-ROBOT SDK & AI Agents (MCP)
Beta Open

Local or cloud scripts, dashboards, smart-home routines, and Claude / AI workflows.

ENTRY 02 · ON-ROBOT ISOLATION Isolated Edge Sandbox
Project Pilot

CPU & memory-capped sandbox for low-latency vision and algorithms—crash-isolated from core drive.

NON-BYPASSABLE SAFETY GATE Core Safety Supervisor
  • Owner Consent & Revocation
  • Bounded Speed & Watchdog
  • Hardwired E-Stop Priority
BASE · RUGGED MOBILITY Tracked Core & Sensors
Core Chassis

Centimeter RTK, wheel/IMU dead-reckoning, stereo vision, battery, and heavy-duty tracked drive.

PAYLOAD · MECHANICAL & BUS Quick-Swap Hardware Kit (HDK)
Custom Mounts

3D CAD mechanical flange, switched power rail, isolated CANopen, and 100BASE-TX Ethernet.

MODULAR ARCHITECTURE · INTERACTIVE X-RAY J4 + J19 · 26–42V · CAN 1Mbps · 100BASE-TX
Yarbo modular tracked robot core surrounded by quick-swap attachments
NODE 01 · FRONT INTERFACE Quick-Swap Attachment Bus

One rugged core, built to bolt onto

Click or hover a node on the robot to inspect what the SDK and Hardware Kit expose.

What’s opening on the platform

Positioning & Status

Beta Open
  • Centimeter-level RTK signal
  • Live position & heading
  • Battery, power & motor load

Vision & On-Robot Apps

Project Pilot
  • Stereo camera snapshots
  • Isolated on-robot Linux apps
  • Low-latency local data access

Maps & Schedules

Beta Open
  • Work zones, paths & no-go areas
  • Read & update work plans
  • Automated time schedules

Movement & Task Control

Guarded Access
  • Start, pause, dock & undock
  • Short-range drive without GPS
  • Custom path following

Modules & Attachments

Hardware Kit
  • Mower, snow blower & leaf blower
  • 3D CAD mount models
  • Power, CAN & Ethernet

AI Assistants

Beta Open
  • Ready-to-use MCP integration
  • Works with Claude & AI agents
  • Explicit approval before actions

See how SDK calls drive a real yard mission

GARAGE · NO GPS drive_odom(3.0m) RTK_FIX LOCK · 1.3cm WORK ZONE A · PLAN #1 NO-GO ZONE
MISSION PHASE UNDOCK & ODOM EXIT
LOCALIZATION WHEEL + IMU ODOM
LIVE POSE x=0.8m · y=0.0m · θ=0°

Clean SDK, built-in safety

Connect with your Yarbo account to inspect live robot status, preview schedule edits before saving, or automate routine tasks in a few readable lines.

  • Zero-write preview before applying map or schedule changes
  • Automatic readback verification on saved updates
  • Ready-to-use MCP server for Claude & AI coding agents
Read Platform Docs →
Python 3.11+
from yarbo_sdk import YarboAccount

with YarboAccount() as account:
    account.login(email, password)
    robot = account.robot(account.devices()[0].device_id)

    snap = robot.status()
    print("Battery:", snap.value("/BatteryMSG/capacity"), "%")
    print("RTK:", snap.value("/RTKMSG/status"))
OUTPUT Battery: 94 % | RTK: RTK_FIX (horiz=0.014m, age=0.2s)

What you could build

Concepts for home snow clearing, smart irrigation, and lawn care

Homeowners

Make yard work fit your routine

Create yard dashboards, smart home automations, or custom attachments tailored to your property.

Concepts for service visits, site reports, scheduling, and commercial yard work

Dealers & property teams

Spot issues early, save trips

Check owner-authorized robot status remotely to prioritize dispatch and keep clear service records.

Concepts for outdoor navigation research and a prototype field-sampling attachment

Universities & labs

Take robotics into the field

Test navigation algorithms, run repeatable outdoor trials, and prototype research tools on a ready-made chassis.

How to join

Apply above ↑
  1. Apply

    Enter your email above. Cohorts are invited in batches.

  2. Get invited

    Approved applicants receive an email within 5 business days.

  3. Start building

    Sign in to the workspace, authorize your robot, and read your first status.

Frequently asked questions

Is the Open Platform Beta free to join?

Yes. Joining the private beta and building personal, academic, or community non-commercial projects is free under the PolyForm Noncommercial 1.0.0 license.

Do I need to own a Yarbo robot right now to apply?

You can apply either way. Connecting to a live robot requires your own Yarbo unit (or explicit authorization from a robot owner), while recorded sample data and 3D mount models are available for offline evaluation first.

What interfaces and development environments are supported?

The beta release opens our software SDK, ready-to-use MCP integration for AI assistants, and Hardware Kit (HDK) 3D CAD mounts with switched power, CAN, and Ethernet specs, plus pilot support for isolated on-robot Linux apps.

Can dealers or companies build commercial tools and services?

Commercial products, fleet operations tools, and paid integrations require a separate written commercial license from Yarbo. Apply above or reach out via software@yarbo.com to discuss partnership terms.

Yarbo Data SDK Terms of Use

Version: V1.1 | Effective Date: October 10, 2026 | Last Updated: November 17, 2026


By downloading, cloning, copying, compiling, accessing or otherwise using the SDK, or by registering a Developer account or submitting an application for Developer qualification, the Developer agrees to be bound by these Terms and confirms that it has read and understood them. If the Developer does not agree to these Terms, the Developer must immediately stop using the SDK and the cloud interfaces.

Article 1 Definitions and Scope of Application

1.1 "We" means Yarbo International, Inc. ("Yarbo") and its affiliates.

1.2 "SDK" means the software development kit, sample code, interface documentation, development materials and related interface capabilities that we provide or update from time to time.

1.3 "Cloud Services" means the device cloud services operated by us, including the account system, authentication services and message subscription services.

1.4 "Developer Application" means any software, plugin, integration, service or tool developed, distributed or operated by a Developer based on the SDK.

1.5 "Developer" means the individual or entity that accepts these Terms and is permitted to access the SDK. Where a Developer accepts these Terms on behalf of a corporate entity, the Developer represents and warrants that it has obtained due authorization from that entity.

1.6 "Authorized Access Scope" means the interfaces, message channels (Topics) and scope of data that we expressly make available to the Developer through written documents, official documentation, the Developer Console or other official channels.

1.7 "Device Data" means data relating to an end user's own device that is generated in the course of the operation, status and working processes of that device.

1.8 "In writing" includes paper documents, emails and electronic confirmations within the Developer Console.

1.9 "Developer Console" means the online management interface and the official developer platform that we provide for Developers (including the developer portal and the access management back office).

1.10 These Terms apply to all use by the Developer of the SDK and the Cloud Services, and together with the Yarbo Terms of Service and the Yarbo Privacy Policy separately published by us form part of the agreement between the parties, and in the event of any conflict regarding the use of the SDK and the cloud interfaces, these Terms shall prevail over the Yarbo Terms of Service and the Yarbo Privacy Policy.

1.11 The Developer represents and warrants that it is at least 18 years of age or has reached the age of majority under the laws of its place of residence, has full capacity to enter into these Terms, and, where it accepts these Terms on behalf of an entity, has obtained due authorization from that entity and may bind it.

Article 2 Acceptance and Effectiveness

2.1 The Developer shall be deemed to have read, understood and agreed to these Terms by any of the following means: downloading, cloning, copying, compiling or using the SDK; registering a Developer account; calling the cloud interfaces; submitting an application for Developer qualification through our official website or the Developer Console; or clicking "Agree".

2.2 These Terms take effect on October 10, 2026, apply to all use occurring on or after the effective date, and may be amended in accordance with Article 16. Where the Developer began using the SDK before the effective date and continues to use it after the effective date, the Developer shall be deemed to have accepted these Terms as of the effective date. A revised version of these Terms applies to all use occurring on or after the date on which it is published on the Developer Platform.

2.3 If the Developer does not agree to these Terms, the Developer shall immediately stop using the SDK and the cloud interfaces.

2.4 Where, before the effective date of these Terms, the Developer has engaged in any provision of the Developer Application to third parties or any commercialization prohibited by these Terms, the Developer shall, within 30 days from the effective date, cease such conduct, cease distributing and charging for the relevant application, and remove it from distribution. If the Developer fails to do so within that period, we have the right to suspend or terminate its permissions in accordance with Article 11. If the Developer continues such conduct after the effective date, it constitutes a continuing breach of these Terms.

2.5 These Terms are published on our official developer platform (the "Developer Platform"), and Developers are prompted to review them when registering or onboarding on that platform. A Developer's downloading, cloning, copying, compiling or use of the SDK constitutes the Developer's acceptance of these Terms and its confirmation that it has read and understood them. The version and the publication and update dates of these Terms are evidenced by the release records on the Developer Platform.

Article 3 Scope of License

3.1 Provided that the Developer continuously complies with these Terms, we grant the Developer a limited, non-exclusive, non-transferable, non-sublicensable and revocable license to:

(1) use the SDK for personal learning, research and testing purposes;

(2) read data within the Authorized Access Scope and write data where we expressly permit; and

(3) develop Developer Applications for the Developer's own use only, or for internal use within the Developer's own enterprise (for the management of that enterprise's own devices).

3.2 Except as expressly permitted under Section 3.1, the Developer shall not use the SDK for any other purpose; in particular, the Developer shall not provide the Developer Application to any third party in any form — whether or not for a fee, and whether by sale, distribution, open-source release or gift, or by obtaining economic benefit through donations, sponsorships, advertising revenue sharing or any other form.

3.3 If the Developer wishes to obtain any authorization beyond Section 3.1 (including but not limited to providing the Developer Application to others, commercial operation, or providing services to consumers), it shall contact us to obtain written authorization (email for authorization requests: software@yarbo.com). Before obtaining such written authorization, the Developer shall not engage in such conduct. Our failure to grant written authorization shall not be deemed an implied license.

3.4 All intellectual property rights and other rights in and to the SDK and related data belong at all times to us or our licensors. Except for the rights expressly granted under these Terms, we reserve all rights.

3.5 The SDK source code is provided under the open-source license terms separately published by us (currently the PolyForm Noncommercial License 1.0.0). The open-source license terms govern only the copying, modification and redistribution of the source code. The Developer's access to and use of the Cloud Services, interfaces, message channels (Topics) and data are granted solely under these Terms, and the open-source license terms do not constitute such authorization. Any provision to third parties of results derived from secondary development of the source code remains subject to Section 3.2 and Article 8.

3.6 The SDK may include third-party components and open-source components. Such components are governed by the applicable third-party or open-source license terms, which prevail over these Terms with respect to those components; we make no additional representation or warranty with respect to them. Copies of the applicable license terms are included in the documentation supplied with the SDK.

Article 4 Access Scope and Technical Boundaries

4.1 The Developer's access to the Cloud Services is strictly limited to the Authorized Access Scope. Any interface, message channel or data that we have not expressly made available falls outside the authorized scope.

4.2 The Developer shall not engage in any of the following:

(1) accessing, subscribing to, probing or enumerating any interface, message channel or data that we have not expressly made available, or publishing to any such interface or message channel;

(2) using wildcards, prefix matching, bulk enumeration, dictionary guessing or similar methods to obtain data beyond the Authorized Access Scope;

(3) obtaining unauthorized data by means of packet capture, sniffing, reverse proxying, forging client identifiers, reusing another person's credentials, replaying requests, or tampering with request headers or protocol fields;

(4) bypassing or circumventing, by any technical means, the authentication, authorization, access control, rate limiting, frequency control or other security measures implemented by us on the cloud side;

(5) reverse engineering, decompiling or cracking the SDK, the Cloud Services or the device communication link, or conducting security testing without our prior written consent;

(6) calling interfaces at a frequency clearly beyond reasonable limits, or engaging in conduct that may affect the stability of the Cloud Services or the normal use of other users.

4.3 The Authorized Access Scope is governed by our then-effective written documents or official instructions. We have the right to adjust, restrict or close any interface, message channel or scope of data at any time based on product, security and compliance needs, without the Developer's consent and without thereby incurring any liability for damages.

4.4 The Developer shall not, through the SDK, issue instructions to devices that may damage a device, cause a device to operate beyond its designated boundary or lose control, endanger personal or property safety, or violate applicable law.

4.5 The Developer understands and agrees that data outside the Authorized Access Scope is data we have not made available, and that regardless of whether it is technically accessible, accessing it constitutes a breach of these Terms and may entail corresponding legal liability.

Article 5 Prohibited Conduct

5.1 The Developer shall not engage in any of the following:

(1) using the Developer Application to manufacture, sell or provide products or services that directly compete with our own products or services;

(2) reselling, renting, lending, sublicensing or otherwise providing the SDK, account permissions or cloud interface access capabilities to any third party;

(3) using shared accounts, bulk-registering accounts, or registering multiple accounts in order to circumvent restrictions;

(4) using or keeping any end user's account and password, whether for itself or on behalf of others (see Article 6);

(5) using data provided by us to train, fine-tune or evaluate any artificial intelligence model, for user profiling or advertising targeting, or for any purpose not directly necessary for the functions of the Developer Application;

(6) removing, obscuring or modifying any copyright, trademark, source or other proprietary notices contained in the SDK or the data;

(7) using expressions such as "Yarbo Official", "Yarbo Certified" or "Yarbo Partner" in promotional materials, or using our trademarks or logos in a manner that creates confusion as to official endorsement or partnership (see Article 9);

(8) using the SDK in a manner that violates applicable laws, regulations, export control or sanctions requirements.

Article 6 Accounts, Authentication and Security

6.1 The Developer shall apply for Developer qualification through our official process; the application conditions and approval criteria shall be separately determined by us.

6.2 The Developer shall properly safeguard its Developer credentials and any user authorization credentials obtained, and shall not disclose, lend or transfer them. Upon discovering any credential leakage or abnormal access, the Developer shall notify us within 24 hours and immediately take remedial measures.

6.3 The Developer is responsible for all activities occurring under its Developer account.

6.4 The Developer shall comply with the access specifications, rate limiting rules and security requirements published by us from time to time.

6.5 If the Developer needs to access an end user's Device Data on that user's behalf, it must obtain the user's authorization through the official authorization mechanism provided by us, shall not ask users to provide account passwords, and shall not keep credentials on users' behalf. Where a user withdraws authorization, the Developer shall immediately stop the corresponding access and delete the data it has obtained.

6.6 We have the right to require the Developer to provide written explanations regarding its use of the SDK and the Cloud Services (including the interfaces called, the message channels subscribed to, data processing and any provision to third parties), and to provide necessary supporting materials within a reasonable period designated by us. Where a material change to the Developer Application may affect compliance with these Terms, the Developer shall notify us in writing in advance.

Article 7 Data Protection and Privacy

7.1 The SDK does not make end-user data available to Developers, nor does it provide bulk query or export capabilities for end-user data. Where an end user, through the official authorization mechanism provided by us, authorizes a Developer to access the Device Data of that user's own device, the Developer may access that user's Device Data within the scope of such authorization (Section 1.7), and these Terms do not affect the application of Section 6.5. Apart from such authorized access, if the Developer needs to obtain any end-user data, it must separately obtain our written permission in advance and sign the relevant agreement before doing so; before obtaining such written permission and signing the relevant agreement, the Developer shall not obtain, use or retain such data in any manner.

7.2 Developers that access end-user data, whether through the official authorization mechanism or under a separate written permission granted by us, shall comply with applicable data protection laws (including but not limited to the GDPR, the CCPA/CPRA and other applicable laws of the jurisdictions in which the Developer and users are located), and shall:

(1) collect and process only the minimum scope of data necessary to implement the functions of the Developer Application;

(2) provide the user with adequate notice and obtain the user's consent before collection (and obtain separate consent where sensitive personal information is involved), and provide users with a clear and accessible privacy notice;

(3) not provide, share or further entrust the data to any third party, or use it for any other purpose, without our prior written consent;

(4) adopt technical and organizational measures commensurate with the sensitivity of the data (encrypted transmission and storage, access control, log retention, etc.);

(5) promptly delete or anonymize the relevant data upon termination of the authorization or withdrawal of the user's consent, and provide users with a channel through which users may submit data access, correction and deletion requests; and

(6) where the SDK automatically collects or transmits any usage statistics, diagnostic data or other information about the Developer Application or its users, disclose this clearly to users in its privacy notice and obtain any consent required by applicable law.

7.3 In the event of a security incident involving our data, the Developer shall notify us in writing within 24 hours, explaining the nature of the incident, the scope of impact and the measures taken, and shall cooperate with us in fulfilling our notification and reporting obligations to users and regulators.

7.4 These Terms grant the Developer no right to redistribute any data. Except with our prior written consent, the Developer shall not provide, sell or share any data obtained under these Terms with any third party, nor use such data to train, fine-tune or evaluate any artificial intelligence model.

7.5 The SDK may automatically collect and transmit to us certain usage statistics, event data, title data, diagnostic logs and device information relating to the Developer's use of the SDK and the Developer Application (for example, SDK version, application identifier, installation identifier, interface calls, error reports and performance metrics). We use such data for purposes including improving the SDK and our products, ensuring security and troubleshooting. Such data does not include end-user personal data unless the end user has separately authorized it through the official authorization mechanism; where personal data is involved, we process it in accordance with the Yarbo Privacy Policy.

Article 8 Commercial Use and Authorization

8.1 The provision to third parties prohibited under Section 3.2 includes, without limitation, the following forms of commercialization: subscription fees, one-time fees, per-use fees, bundling, advertising monetization, accepting donations or sponsorships, obtaining financing or investment consideration with the Developer Application as the subject matter, and white-labeling or operating on behalf of others.

8.2 Where the Developer breaches Section 3.2 or Section 8.1, we have the right to immediately suspend or terminate its account and interface permissions, and to require it to cease the relevant conduct, remove the relevant application from distribution, and bear liability for breach of contract.

8.3 A plugin that a Developer submits through the Developer Console and that we approve and publish on our platform is deemed to have obtained the written authorization required under Section 3.2 for that publication and distribution. The submission, review, publication, removal and (if applicable) charging rules for such plugins will be governed by the developer publication policy that we publish; until that policy is formally issued, the relevant requirements will be notified separately through the Developer Console or in writing.

Article 9 Intellectual Property and Trademarks

9.1 All intellectual property rights in the SDK, the Cloud Services, the device firmware, the data and derivative works thereof belong to us.

9.2 With our written permission, the Developer may state, in a descriptive manner, that its Developer Application is "compatible with Yarbo devices", provided that it also prominently indicates "unofficial product / independent third-party product", and it shall not use our trademarks or logos as the application name, icon or primary identifier.

9.3 We may freely use any feedback, suggestions or defect reports submitted to us by the Developer, without payment of any consideration. Feedback does not constitute confidential information, and we assume no obligation of confidentiality, return or compensation with respect to it.

9.4 The Developer shall prominently state, in its Developer Application's user agreement, privacy notice and promotional materials, that it is an independent third party, that its application is independent of our products and Cloud Services, that the application is provided by the Developer itself and the Developer bears all responsibility for it, and that we make no warranty or endorsement with respect to the application.

Article 10 Confidentiality

10.1 "Confidential Information" means non-public information disclosed by us or on our behalf to the Developer in connection with the SDK, the Cloud Services, the Developer Console or our products and business, in any form, including the source code of any non-public portion of the SDK, interface documentation, credentials, unreleased features, roadmaps, pricing, launch plans, security measures, and any test results or evaluation conclusions, as well as any analysis or report prepared by the Developer that contains or reflects such information.

10.2 Information does not constitute Confidential Information where the Developer can demonstrate with written records that it: (a) was lawfully in the public domain at the time of disclosure; (b) entered the public domain without breach by the Developer; (c) was lawfully held by the Developer before disclosure and free of any confidentiality obligation; (d) was lawfully obtained from a third party entitled to disclose it and free of any confidentiality obligation; or (e) was independently developed by the Developer without use of or reference to the Confidential Information.

10.3 The Developer shall protect the Confidential Information with at least the degree of care it applies to its own confidential information of similar importance and in no event less than reasonable care, shall use it only to the extent necessary to exercise the rights expressly granted under these Terms, and shall not disclose it to any third party except to its employees, contractors or professional advisers who need to know it for that purpose and are bound by written confidentiality obligations no less protective than this Article.

10.4 The confidentiality obligations under this Article apply during the term of these Terms and for three (3) years after termination. Information that constitutes a trade secret under applicable law shall remain protected for as long as it continues to constitute a trade secret, and the source code of any non-public portion of the SDK shall remain confidential indefinitely.

10.5 If the Developer is required by law, regulation, subpoena or an order of a court or regulator to disclose Confidential Information, the Developer shall, to the extent permitted by law: (a) promptly notify us in writing in advance; (b) reasonably cooperate with us in seeking a protective order; and (c) disclose only the portion legally required.

10.6 Upon discovering any unauthorized use, disclosure or loss of Confidential Information, the Developer shall notify us in writing within 24 hours and shall immediately take remedial measures.

10.7 Where the Developer has entered into a separate confidentiality agreement with us (including the SDK beta confidentiality agreement), that agreement governs the confidential information covered by it; in the event of any inconsistency, the provision more protective of our Confidential Information shall apply.

Article 11 Service Changes, Suspension and Termination

11.1 We have the right to change, restrict, suspend or terminate any part of the SDK and the cloud interfaces based on security, compliance, product planning or operational needs.

11.2 We have the right to immediately suspend or terminate the Developer's permissions, without prior notice, and to pursue legal liability, if the Developer:

(1) breaches Article 4 (Access Scope and Technical Boundaries);

(2) breaches Article 8 (Commercial Use);

(3) causes or may cause risks to data security, network security, device safety or personal safety; or

(4) otherwise materially breaches these Terms.

11.3 Upon termination of these Terms, the Developer shall immediately stop using the SDK and the cloud interfaces, delete all Confidential Information and all other data it holds within 30 days of termination (except where retention is required by applicable law), confirm such deletion to us in writing upon request, and cease all provision to third parties and all commercialization. Articles 6, 7, 9, 10, 12, 13, 14, 15, 17 and 18 shall survive termination.

Article 12 Disclaimer and Limitation of Liability

12.1 The SDK and the cloud interfaces are provided "as is". We make no express or implied warranty as to their availability, continuity, accuracy, error-free operation or fitness for a particular purpose. We do not undertake to provide technical support, maintenance or updates, and we make no service level or availability commitment.

12.2 The Developer Application is independently developed and operated by the Developer, which bears full responsibility for it. Any damage to a device, operation of a device beyond its designated boundary or loss of control, personal injury, property damage, data breach or third-party claim caused by or relating to the Developer Application or its use shall be borne entirely by the Developer, and we shall bear no liability. During the beta or internal testing stage, the capabilities, interfaces, data scope and availability of the SDK may be changed, restricted or discontinued at any time.

12.3 To the maximum extent permitted by applicable law, we shall bear no liability to the Developer. To the maximum extent permitted by applicable law, the Developer waives any claim, action or assertion against us with respect to the provision, use, inability to use, interruption, delay, error or defect of the SDK, the Cloud Services or the interfaces, loss of or damage to data, changes to or termination of services, and any direct, indirect, incidental, special, punitive or consequential losses arising therefrom (including but not limited to loss of profits, business interruption and the cost of substitute services), whether based on contract, tort, negligence, strict liability or any other legal basis, and whether or not we have been advised of the possibility of such losses. Nothing in this Section excludes any liability that cannot be excluded under applicable law.

12.4 Except for liability that may not be excluded under applicable law (including liability arising from our fraud, willful misconduct or gross negligence), our liability to the Developer is zero. We assume no obligation of compensation, reimbursement or contribution arising from the execution of these Terms, the provision of the SDK or the Developer's use of the SDK.

12.5 If any exclusion or limitation of liability in these Terms is held unenforceable by a competent authority, the remaining provisions shall continue in effect, and we reserve all defenses, statutes of limitation and limitations of liability available under applicable law.

12.6 The Developer acknowledges that the SDK is currently provided free of charge, that we reserve the right to charge fees for specific uses, and that the above disclaimers and limitations of liability constitute a reasonable allocation of risk between the parties and are the basis on which we provide the SDK; absent this agreement, we would not provide the SDK.

Article 13 Developer's Indemnification Obligations

13.1 The Developer shall fully indemnify and hold us and our affiliates, directors, officers, employees, agents and customers harmless against any claim, action, arbitration, investigation, administrative penalty, loss or expense (including reasonable attorneys' fees, expert fees, settlement amounts and judgment amounts) arising from any of the following:

(1) the Developer Application itself or its content;

(2) the Developer's breach of any provision of these Terms, in particular Articles 4, 6, 7, 8, 10 and 14;

(3) the Developer's infringement of any third party's intellectual property rights, privacy rights, data rights or other lawful rights and interests;

(4) damage to a device, operation of a device beyond its designated boundary, personal injury or property damage caused by or relating to the Developer Application.

13.2 The Developer waives any defense or right requiring us first to pursue, pay or assert rights against any third party. We have the right to determine the defense, settlement or litigation strategy at our sole discretion, and the Developer shall cooperate unconditionally and bear the costs arising therefrom.

13.3 Our right to claim indemnification is not affected by our termination of these Terms, suspension of services or imposition of technical restrictions.

13.4 The indemnification obligations under this Article are not subject to any monetary cap.

Article 14 Compliance, Insurance and Security

14.1 The Developer shall ensure on its own that its Developer Application complies with all applicable laws of the places in which it operates and in which users are located, including requirements relating to product safety, radio equipment, consumer protection; export control and sanctions are governed by Article 15.

14.2 The Developer shall, taking into account the scale of its Developer Application, the types of data involved and the degree of risk, purchase and continuously maintain insurance commensurate with the scale of its development activities, including but not limited to product liability insurance and cyber liability insurance. We do not impose a uniform requirement on the insured amount, but we have the right to require the Developer to provide proof of insurance where reasonably necessary.

14.3 Where the Developer fails to purchase or maintain the insurance described in Section 14.2, all liabilities, losses and claims arising from its Developer Application shall be borne entirely by the Developer, and the Developer shall not claim any contribution, reimbursement or compensation from us.

14.4 Where the Developer discovers a security vulnerability in our products or the Cloud Services, it shall report the vulnerability to us in accordance with the Yarbo Vulnerability Disclosure Policy, shall not publicly disclose any unremedied vulnerability, and shall not exploit any vulnerability to obtain data beyond the Authorized Access Scope.

Article 15 Export Control and Sanctions

15.1 The SDK, the Cloud Services and any related technology, documentation and technical data may be subject to the export control and economic sanctions laws of the United States (including the Export Administration Regulations) and of other applicable jurisdictions. The Developer shall not export, re-export, transfer or otherwise make the SDK or such technology, documentation or technical data available to any country, territory, entity or person subject to comprehensive sanctions or restrictions, or use them for any prohibited end use, including nuclear, chemical or biological weapons or missile technology applications.

15.2 The Developer represents and warrants that it is not located in, organised under the laws of, or ordinarily resident in any comprehensively sanctioned country or territory, and is not owned or controlled by, or acting on behalf of, any person identified on any applicable restricted party list, including the U.S. Consolidated Screening List. The Developer shall comply with all applicable export control and sanctions requirements and shall notify us promptly if any of the above representations ceases to be true.

15.3 We may suspend or terminate the Developer's access immediately where we reasonably consider this necessary to comply with export control or sanctions requirements, and the Developer shall not claim any compensation for such suspension or termination.

Article 16 Notices and Amendments

16.1 Notices given by us may be sent to the Developer's registered email address or published through the Developer Console, and are deemed served on the date of sending or publication, as applicable.

16.2 We have the right to amend these Terms, and following any amendment we will update the version date and notify the Developer in the manner described above. We will give the Developer 30 days' prior written notice of material amendments (including changes to the access scope, the commercial use restrictions, and the liability and indemnity provisions). Where a Developer has not registered a Developer account, material amendments will also be announced by publication of a notice on our official developer platform. A Developer's continued use of the SDK after the expiration of the aforementioned notice period constitutes acceptance of the amendments.

Article 17 Governing Law and Dispute Resolution

17.1 The formation, validity, interpretation, performance and dispute resolution of these Terms shall be governed by the laws of the State of Illinois, United States, without regard to its conflict-of-laws rules and without application of the United Nations Convention on Contracts for the International Sale of Goods.

17.2 Any dispute, controversy or claim arising out of or relating to these Terms shall first be resolved through negotiation. Negotiation shall commence within 7 days after one party sends a written request for negotiation; if the dispute is not resolved within 30 days after the commencement of negotiation, either party may submit the dispute to the Circuit Court of Cook County, Illinois, and the United States District Court for the Northern District of Illinois (both located in Chicago, Illinois), and the parties irrevocably consent to the exclusive jurisdiction of such courts.

Article 18 Miscellaneous

18.1 If any provision of these Terms is held invalid or unenforceable, the validity of the remaining provisions shall not be affected.

18.2 The Developer may not assign its rights or obligations under these Terms; we may freely assign.

18.3 Except as otherwise provided in these Terms, these Terms, together with the access specifications and security requirements separately published by us and any confidentiality agreement separately entered into by the parties, constitute the entire agreement between the parties with respect to the SDK.

18.4 These Terms are drafted and published in English, and the English version is the sole authentic and controlling version. Any translation or text in another language is provided for convenience only, is not binding, and shall not affect the interpretation of these Terms.

18.5 Our failure or delay in exercising any right under these Terms shall not constitute a waiver of that right.

18.6 Article headings are for ease of reference only and shall not affect the interpretation of these Terms.

18.7 Nothing in these Terms creates any agency, partnership, joint venture or employment relationship between the parties, and the Developer has no authority to make any representation or commitment, or to assume any obligation, on our behalf.